This repository was archived by the owner on May 29, 2026. It is now read-only.
chore(docs): sync development -> documentation for deploy#188
Merged
Conversation
Defense against supply-chain attacks (e.g. shai-hulud, nx-style compromised publishes) by blocking install of any package version published less than 24h ago. - .npmrc: `min-release-age=1` (npm 11.5+ native; older npm ignores it) - .github/dependabot.yml: `cooldown.default-days: 1`, with @conduction/* excluded so first-party releases reach our apps immediately For release-day consumption of fresh @conduction/* deps, use `npm install --min-release-age=0 @conduction/pkg@x.y.z`.
Brings mydash's openspec/changes/ under Hydra's ADR-032 spec-sizing gate (cap: 20 unchecked tasks per change). Mix of CASE A (multi-spec bundle split into N per-capability changes) and CASE B (single-spec with too many tasks → trim tasks.md by collapsing nested sub-checkboxes). All semantic content preserved — only tasks.md restructured (Case B) or change-folder boundaries redrawn (Case A). Spec deltas, proposal motivations, and design decisions kept verbatim where untouched. Audit verified post-edit: zero change folders over 20 unchecked tasks (grep -cE '^\s*-\s+\[ \]' across openspec/changes/*/tasks.md = 0). Part of fleet-wide Wave 2 (8 apps, 60 changes) following the shillinq foundation pattern (#91) + Wave 1.2 (#94) precedent.
spec(mydash): bring all changes under ADR-032 20-task cap (Wave 2)
- Add 1200x630 brand OG card at docs/static/img/og-mydash.png with the app's wordmark + tagline, replacing the preset's generic Conduction card on social/LinkedIn/AI previews. - Set themeConfig.image to reference the new card. - Correct llms.txt docs links to point at /docs/intro and /api, which match the actual route structure on mydash.conduction.nl (the prior /tutorials, /Features, /UseCases links 404 on the live site).
Drop the local docs/scripts/validate-ai-baseline.mjs copy and call the bin command shipped by @conduction/docusaurus-preset >=3.5.0 instead. Why: keeps the validator in one place across the fleet. Future check additions ship via a preset bump rather than 17 parallel PRs. Validator behaviour is identical (same 8 universal checks).
Preset 3.6.0 ships the traditional-SEO baseline (sitemap lastmod, drops priority/changefreq per Google 2026 guidance, fixes the legal- link 404s on subdomain footers, adds searchConsoleVerification opt). The lockfile bump uses --min-release-age=0 per .npmrc cooldown override (required for fresh @conduction/* releases under the 24h supply-chain cooldown).
rubenvdlinde
requested review from
Rem-Dam,
SudoThijn,
WilcoLouwerse,
bbrands02,
remko48 and
rjzondervan
as code owners
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Brings the AI baseline (robots.txt, llms.txt, JSON-LD, OG card, FAQPage, SoftwareApplication) + the traditional-SEO baseline (sitemap lastmod, fixed legal links) onto documentation so the deploy workflow picks them up. Same pattern as previous sync PRs in this repo.